div.b_DuetMap{
    --section_padding_block:40px;
}
@media (width >= 1000px) {
    div.b_DuetMap{
        --section_padding_block:80px;
    }
}


.b_DuetMap .duetMap{
    width:100%;
}


/* BUTTON COLOR */
/* --duet-map-accent drives the legend checkboxes and the info-window links. */
.b_DuetMap .button_primary{
    --duet-map-accent:var(--color_primary);
}
.b_DuetMap .button_secondary{
    --duet-map-accent:var(--color_secondary);
}
.b_DuetMap .duet-map__check
{
    border: 2px solid var(--color_honey_glow);
}
/* The search button is a <button type="submit"> inside a form, so the theme's
   `form [type=submit]` (:is(.block) form [type=submit], 0-2-1) claims it and
   REDECLARES --button_background_color and friends on the button itself. A
   declaration on the element always beats one inherited from an ancestor, so
   these have to be set on the button, not on the map root. Three classes
   clears 0-2-1. The theme still supplies the border width, font and padding,
   so the button keeps the site's button design. */
.b_DuetMap .button_primary .duet-map__search-button{
    --button_background_color:var(--color_primary);
    --button_border_color:var(--color_primary);
    --button_text_color:var(--color_manilla_lighter);
}
.b_DuetMap .button_secondary .duet-map__search-button{
    --button_background_color:var(--color_secondary);
    --button_border_color:var(--color_secondary);
    --button_text_color:var(--color_manilla);
}
/* Inverted fill on hover, matching the theme's own coloured buttons
   (.warm_horizon, .evergreen). Beats :is(.block) button:hover (0-2-1);
   the form [type=submit] rule has no hover state of its own. */
.b_DuetMap .duet-map__search-button:hover{
    --button_background_color:var(--color_manilla_lighter);
    --button_border_color:var(--duet-map-accent);
    --button_text_color:var(--duet-map-accent);
}
/* The plugin also dims the button to 0.85 on hover and focus, which would
   wash out that fill. The colour change is the affordance. */
.b_DuetMap .duet-map__search-button:hover,
.b_DuetMap .duet-map__search-button:focus{
    opacity:1;
}


/* LEGEND LINK */
/* Same override as the button: :is(.block) a{color:inherit} (0,1,1) beats
   .duet-map__legend-link (0,1,0), so the accent is restated block-scoped. */
.b_DuetMap .duet-map__legend-link{
    color:var(--duet-map-accent);
}


/* COLUMN BACKGROUND */
.b_DuetMap .bg_honey_glow .duet-map__body{
    background-color:var(--color_honey_glow);
}


/* INTRO COLUMN */
/* The plugin ships --duet-map-intro-padding at 0, which leaves the heading
   and the search field flush against the edge of the column. */
.b_DuetMap .duet-map__intro{
    --duet-map-intro-padding:30px;
}


/* NO GAP BETWEEN THE COLUMN AND THE MAP */
/* The 30px above is the only spacing wanted, so drop the grid gap and let
   the column sit flush against the map canvas. */
.b_DuetMap .duetMap{
    --duet-map-gap:0;
}
/* --duet-map-gap also drove the space above the legend, so put that back. */
.b_DuetMap .duet-map__legend{
    margin-top:32px;
}


/* STAFF MAPS */
/* Three full-width rows: intro, map, legend. The plugin adds
   .duet-map--staff itself, and only once a staff dataset really renders. */
.b_DuetMap .duet-map--staff .duet-map__body{
    grid-template-columns:1fr;
}
.b_DuetMap .duet-map--staff .duet-map__intro{
    align-items:center;
    text-align:center;
}
.b_DuetMap .duet-map--staff .duet-map__search-form{
    justify-content:center;
}
/* Contained again — this row is now the full page width. The 10px corners
   come from the base rule below and apply to both layouts. */
.b_DuetMap .duet-map--staff .duet-map__search-input{
    /* flex:0 1 385px;
    max-width:385px; */
}


/* ADDRESS FIELD */
/* Full width: a 100% flex-basis fills the row, which wraps the button
   onto its own line underneath. */
.b_DuetMap .duet-map__search-input{
    flex:1 1 100%;
    max-width:none;
    border-radius:10px;
}